| Package | hl7.ehrs.ehrsfmr21 |
| Type | Requirements |
| Id | Id |
| FHIR Version | R5 |
| Source | http://hl7.org/ehrs/https://build.fhir.org/ig/mvdzel/ehrsfm-fhir-r5/Requirements-EHRSFMR2.1-POP.1.1.html |
| Url | http://hl7.org/ehrs/Requirements/EHRSFMR2.1-POP.1.1 |
| Version | 2.1.0 |
| Status | active |
| Date | 2024-11-26T16:30:50+00:00 |
| Name | POP_1_1_Present_Alerts_for_Preventative_Services_and_Wellness |
| Title | POP.1.1 Present Alerts for Preventative Services and Wellness (Function) |
| Experimental | False |
| Realm | uv |
| Authority | hl7 |
| Description | Identify patient-specific suggestions/reminders, screening tests/exams, and other preventative services in support of routine preventative and wellness care. |
| Purpose | At the time of an encounter, the provider or patient is presented with due or overdue activities based on protocols for preventative care and wellness. Examples include routine immunizations, adult and well child care, age and gender appropriate screening exams, such as PAP smears. |
No resources found
No resources found
Note: links and images are rebased to the (stated) source
Identify patient-specific suggestions/reminders, screening tests/exams, and other preventative services in support of routine preventative and wellness care.
At the time of an encounter, the provider or patient is presented with due or overdue activities based on protocols for preventative care and wellness. Examples include routine immunizations, adult and well child care, age and gender appropriate screening exams, such as PAP smears.
| POP.1.1#01 | SHALL |
The system SHALL provide the ability to manage criteria for disease management, wellness, and preventative services based on patient demographic data (minimally age and gender). |
| POP.1.1#02 | SHOULD |
The system SHOULD provide the ability to capture and maintain the rules or parameters upon which guideline-related alerts are based. |
| POP.1.1#03 | SHOULD |
The system SHOULD provide the ability to manage clinical decision support criteria for disease management, wellness, and preventative services based on clinical data (e.g., problem/diagnosis list or current medications). |
| POP.1.1#04 | SHALL |
The system SHALL provide the ability to render alerts based on recognized-standard guidelines, and/or locally-defined standard guidelines. |
| POP.1.1#05 | SHOULD |
The system SHOULD provide the ability to render a list of all alerts along with the scheduled date and time for the preventative care and wellness. |
| POP.1.1#06 | MAY |
The system MAY provide the ability to render a history of all alerts that were generated for the patient in the record. |
| POP.1.1#07 | SHOULD |
The system SHOULD provide the ability to capture and maintain reasons disease management or preventative services/wellness prompts were overridden. |
| POP.1.1#08 | SHOULD |
The system SHOULD provide the ability to capture and maintain documentation that a preventative or disease management service has been performed based on activities documented in the record (e.g., vitals signs taken). |
| POP.1.1#09 | SHOULD |
The system SHOULD provide the ability to capture and maintain documentation that a disease management or preventative service has been performed with associated dates or other relevant details recorded. |
| POP.1.1#10 | SHOULD |
The system SHOULD provide the ability to capture, maintain and render alerts to individual patients regarding their specific clinical situation. |
| POP.1.1#11 | dependent SHOULD |
The system SHOULD determine when the patient's monitored health parameters have exceeded threshold values according to scope of practice, and/or organizational policy, and transmit an alert to a patient's provider or to the patient's care team. |
| POP.1.1#12 | dependent SHOULD |
The system SHOULD determine and render notifications regarding drug-drug interaction(s) (e.g., drug-drug, drug duplication, drug-disease, drug-allergy, and/or drug-food) to the patient's provider or to the patient's care team when changes are made to a population health decision support rule set according to scope of practice, organizational policy, and/or jurisdictional law. |
FHIR{
"resourceType" : "Requirements",
"id" : "EHRSFMR2.1-POP.1.1",
"meta" : {
"profile" : [
"http://hl7.org/ehrs/StructureDefinition/FMFunction"
]
},
"text" : {
"status" : "extensions",
"div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\">\n <span id=\"description\"><b>Statement <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b> <div><p>Identify patient-specific suggestions/reminders, screening tests/exams, and other preventative services in support of routine preventative and wellness care.</p>\n</div></span>\n\n \n <span id=\"purpose\"><b>Description <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Informative Content\" class=\"informative-flag\">I</a>:</b> <div><p>At the time of an encounter, the provider or patient is presented with due or overdue activities based on protocols for preventative care and wellness. Examples include routine immunizations, adult and well child care, age and gender appropriate screening exams, such as PAP smears.</p>\n</div></span>\n \n\n \n\n \n <span id=\"requirements\"><b>Criteria <a href=\"https://hl7.org/fhir/versions.html#std-process\" title=\"Normative Content\" class=\"normative-flag\">N</a>:</b></span>\n \n <table id=\"statements\" class=\"grid dict\">\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#01</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to manage criteria for disease management, wellness, and preventative services based on patient demographic data (minimally age and gender).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#02</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain the rules or parameters upon which guideline-related alerts are based.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#03</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to manage clinical decision support criteria for disease management, wellness, and preventative services based on clinical data (e.g., problem/diagnosis list or current medications).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#04</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHALL</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHALL provide the ability to render alerts based on recognized-standard guidelines, and/or locally-defined standard guidelines.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#05</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to render a list of all alerts along with the scheduled date and time for the preventative care and wellness.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#06</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>MAY</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system MAY provide the ability to render a history of all alerts that were generated for the patient in the record.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#07</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain reasons disease management or preventative services/wellness prompts were overridden.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#08</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain documentation that a preventative or disease management service has been performed based on activities documented in the record (e.g., vitals signs taken).</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#09</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture and maintain documentation that a disease management or preventative service has been performed with associated dates or other relevant details recorded.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#10</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD provide the ability to capture, maintain and render alerts to individual patients regarding their specific clinical situation.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#11</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine when the patient's monitored health parameters have exceeded threshold values according to scope of practice, and/or organizational policy, and transmit an alert to a patient's provider or to the patient's care team.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n <tr>\n <td style=\"padding-left: 4px;\">\n \n <span>POP.1.1#12</span>\n \n </td>\n <td style=\"padding-left: 4px;\">\n \n <i>dependent</i>\n \n \n \n <span>SHOULD</span>\n \n </td>\n <td style=\"padding-left: 4px;\" class=\"requirement\">\n \n <span><div><p>The system SHOULD determine and render notifications regarding drug-drug interaction(s) (e.g., drug-drug, drug duplication, drug-disease, drug-allergy, and/or drug-food) to the patient's provider or to the patient's care team when changes are made to a population health decision support rule set according to scope of practice, organizational policy, and/or jurisdictional law.</p>\n</div></span>\n \n \n </td>\n </tr>\n \n </table>\n</div>"
},
"url" : "http://hl7.org/ehrs/Requirements/EHRSFMR2.1-POP.1.1",
"version" : "2.1.0",
"name" : "POP_1_1_Present_Alerts_for_Preventative_Services_and_Wellness",
"title" : "POP.1.1 Present Alerts for Preventative Services and Wellness (Function)",
"status" : "active",
"date" : "2024-11-26T16:30:50+00:00",
"publisher" : "EHR WG",
"contact" : [
{
"telecom" : [
{
"system" : "url",
"value" : "http://www.hl7.org/Special/committees/ehr"
}
]
}
],
"description" : "Identify patient-specific suggestions/reminders, screening tests/exams, and other preventative services in support of routine preventative and wellness care.",
"jurisdiction" : [
{
"coding" : [
{
"system" : "http://unstats.un.org/unsd/methods/m49/m49.htm",
"code" : "001",
"display" : "World"
}
]
}
],
"purpose" : "At the time of an encounter, the provider or patient is presented with due or overdue activities based on protocols for preventative care and wellness. Examples include routine immunizations, adult and well child care, age and gender appropriate screening exams, such as PAP smears.",
"statement" : [
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-01",
"label" : "POP.1.1#01",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to manage criteria for disease management, wellness, and preventative services based on patient demographic data (minimally age and gender).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.5.1#1"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-02",
"label" : "POP.1.1#02",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain the rules or parameters upon which guideline-related alerts are based.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.5.1#2"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-03",
"label" : "POP.1.1#03",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to manage clinical decision support criteria for disease management, wellness, and preventative services based on clinical data (e.g., problem/diagnosis list or current medications).",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.5.1#3"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-04",
"label" : "POP.1.1#04",
"conformance" : [
"SHALL"
],
"conditionality" : false,
"requirement" : "The system SHALL provide the ability to render alerts based on recognized-standard guidelines, and/or locally-defined standard guidelines.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.5.1#4"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-05",
"label" : "POP.1.1#05",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to render a list of all alerts along with the scheduled date and time for the preventative care and wellness.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.5.1#5"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-06",
"label" : "POP.1.1#06",
"conformance" : [
"MAY"
],
"conditionality" : false,
"requirement" : "The system MAY provide the ability to render a history of all alerts that were generated for the patient in the record.",
"derivedFrom" : "EHR-S_FM_R1.1 DC.2.5.1#6"
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-07",
"label" : "POP.1.1#07",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain reasons disease management or preventative services/wellness prompts were overridden."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-08",
"label" : "POP.1.1#08",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain documentation that a preventative or disease management service has been performed based on activities documented in the record (e.g., vitals signs taken)."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-09",
"label" : "POP.1.1#09",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture and maintain documentation that a disease management or preventative service has been performed with associated dates or other relevant details recorded."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : false
}
],
"key" : "EHRSFMR2.1-POP.1.1-10",
"label" : "POP.1.1#10",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD provide the ability to capture, maintain and render alerts to individual patients regarding their specific clinical situation."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-POP.1.1-11",
"label" : "POP.1.1#11",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine when the patient's monitored health parameters have exceeded threshold values according to scope of practice, and/or organizational policy, and transmit an alert to a patient's provider or to the patient's care team."
},
{
"extension" : [
{
"url" : "http://hl7.org/ehrs/StructureDefinition/requirements-dependent",
"valueBoolean" : true
}
],
"key" : "EHRSFMR2.1-POP.1.1-12",
"label" : "POP.1.1#12",
"conformance" : [
"SHOULD"
],
"conditionality" : false,
"requirement" : "The system SHOULD determine and render notifications regarding drug-drug interaction(s) (e.g., drug-drug, drug duplication, drug-disease, drug-allergy, and/or drug-food) to the patient's provider or to the patient's care team when changes are made to a population health decision support rule set according to scope of practice, organizational policy, and/or jurisdictional law."
}
]
}
XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.